When I said it'd take a hot minute, I apparently meant about an hour or so. Nice job, past me. Thank you, pkgdown and usethis developers. You're the real heroes here. 🐈

Anyway, the website has been updated and updates itself every time something is pushed or pulled. Note to self: Update the internal website documentation.

As an aside, I think this might actually be worse for the environment than us manually re-rendering the site when needed. You win some, you lose some by contributing to climate change, I guess.

As a second more important aside, @tdhock: If you choose to merge this, you'll probably want to go to .github/workflows/pkgdown.yaml and strip branches: [main, master, automatic-birthday-machine] to branches: [master].

I know like nothing about infosec, but the fact that I could force the website to update from a branch and bypass your decision-making feels kinda concerning. Hell, I could go and write "CATS RULE, DOGS DROOL" on the website right now and it'd update without your input. But that's a separate matter.

About infosec, as member of @animint/developers you have maintain permission on this repo.

so this PR would run pkgdown to re-make doc web site during every PR?

I think it would be better to only run that on pushes to master, which I think means removing the pull_request workflow, is that right?

About infosec, as member of @animint/developers you have maintain permission on this repo.

Yeah, that's true. What's new is that .github/workflows/pkgdown.yaml effectively gives us write permission on the website. In practice, not a big problem. I trust that you trust the animint developers. :>

so this PR would run pkgdown to re-make doc web site during every PR?

Yup.

I think it would be better to only run that on pushes to master, which I think means removing the pull_request workflow, is that right?

I'm pretty sure, yeah.